(feat) Added rust sync implementation#20
Merged
Conversation
… C_SHARP sync implementations.
Chriztiaan
changed the title
…ploads after crud upload completes.
…oad on first line read. Sending NOTIFY_TOKEN_REFRESH control on non-expired fetch credentials instruction.
simolus3
reviewed
Dec 3, 2025
stevensJourney
approved these changes
Dec 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This bumps the SDK to use the latest (0.4.9) version of the core extension, it introduces support for the Rust Sync implementation and also makes it the default - users can still opt out and use the legacy C# sync implementation.
Added some integration tests that allowed me to more easily confirm that both sync implementations work as expected. I want to iterate on this over time.
Added some other internal changes which I had on hand that will be used/exposed in a future API update (sync progress/priority changes).
FYI @LucDeCaf